What?

• Ensure merged fontFace data is JSON encoded as an array instead of an object.
• Add a test case to ensure that.

Why?

To fix a bug consisting of fontFace data being JSON encoded as an object ( {...} ) instead of an array ( [...] ).

When we remove duplicates, we could end up with missing sequential array keys in the fontFace list.

Because of the nature of PHP arrays and how they are encoded into JSON. In PHP, arrays can behave like indexed arrays or associative arrays (hashmaps). When they are encoded into JSON, indexed arrays become JSON arrays (e.g., [...]), while associative arrays become JSON objects (e.g., {...}).

The reason fontFace is being encoded as an object in your JSON output is due to the non-sequential keys.

How?

To ensure that fontFace is always encoded as a JSON array, I reset the keys of the $unique_faces array using array_values() before assigning it to $merged_font['fontFace']. This will reindex the keys and make sure they are sequential.

Testing Instructions

Run PHP unit tests with and without calling array_values() on this line:

$merged_font['fontFace'] = array_values( $unique_faces );

$merged_font['fontFace'] =  $unique_faces;

The added test case should fail when array_values() is not used.